Tech Arsenal 1

home *** CD-ROM | disk | FTP | other *** search

/ Tech Arsenal 1 / Tech Arsenal (Arsenal Computer).ISO / tek-20 / ll200e.zip / LAN-DOC.EXE / LAN-DOC.2 < prev

Wrap

Text File | 1992-05-04 | 138KB | 3,422 lines

Appendix 1 LAN-LINK 2.00 Disk Files, Page 114 Appendix 2 LAN-LINK Disk Files The following disk files are associated with the program. LAN-LINK.COM LAN-LINK.SYS *.RUN LAN-LINK.LOG LAN-LINK.DIR CONFIG.SYS *.MBX *.BBS LAN-LINK.001 .. LAN-LINK.010 QBU-RX.BAT QBU-TX.BAT LAN-LINK.QTA QZ*.BAT ELMER.QSO Consider each of them in turn. 1.0 LAN-LINK.EXE This is the program. You activate it from DOS by typing the word LAN-LINK followed by ENTER in the normal manner of invoking DOS commands. 2.0 LAN-LINK.SYS This file contains the configuration information for both the program and the TNC. YOU MUST EDIT IT before you run the program on the air the first time. Use the customization options in the parameters menu to make the changes. The contents of the default file together with an item number are shown below. 1. Callsign 2. Selcal 3. CQ Text 4. CTEXT Line 5. ELMER Flag 6. CQ Delay (seconds) 7. CQ Delay (minutes) 8. :QSP: Message Relay Flag 9. PC Serial Communications Port Number 10. TNC Type 11. PC to TNC Baud Rate 12. VHF Log Book File 13. HF Log Book File 14. GMT Offset 15. Path Directory File name LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 115 16. Brag Tape File name 17. BBS Snatch Mail Trigger Word 18. QTC Snatch Flag 19. BBS Snatch Flag 20. Shut Down Mode 21. PC to TNC Data Bits 22. PC to TNC Parity Bit 23. PC to TNC Stop Bits 24. DCD Flag 25. QBM Download Subdirectory 26. Run File Directory Path 27. BBS Read Request Command 28. Local BBS Callsign 29. SAREX Callsign 30. SAREX Capture to Disk File name 31. PacketCluster Call 32. Digipeat Detect Flag 33. Node Drop Link Flag 34. Sound Flag 35. Display Computer Generated Commands Flag 36. Date/timestamp in Call Sequence Flag 37. Keyboard Character Beep value. 38. :QBU: Receiving Station Batch file (QBU-RX.BAT) 39. :QBU: Originating Station Batch file (QBU-TX.BAT) 40. Capture-to-disk Flag 41. Beacon Control/LAN-LINK handshake Flag 42. Read Bulletin Character 43. BBS Subject String 44. BBS Message String 45. VHF Paclen 46. HF Paclen 47. Beacon Time 48. Number of CQ Lines 49. Word wrap 50. PC Port 4 Custom Address 51. PC Port 4 Custom IRQ 52. VHF Stream switch character 53. HF Stream switch character 54. TNC Error message 55. Connect Timeout Delay 56. Custom Prompt 57. ELMER Configuration File 58. Flag XMITOK 59. Input Message Base Count 60. Default users 61-88. Custom Colors 89. First PacketCluster Command 90. Second PacketCluster Command 91. TNC Mailbox ON Command 92. TNC Mailbox OFF Command 93. VHF Maxframe Command 94. HF Maxframe Command LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 116 95. Start of Scan Words (MUST HAVE AT LEAST ONE) 96. * end of Scan Words 97. Start of Common Calls (MUST HAVE AT LEAST ONE) 98. * end of Common Calls 99. Remaining TNC start up Commands. The contents of each line are described in the section of the Parameters menu which deals with customizing them except for the ones described below. They can only be changed by using the editor. The remaining lines contain commands to the TNC. For further information about them refer to the TNC manual. LAN-LINK assumes different defaults in some instances to those set in the TNC. The SYS file contains only those that are different to the TNC default reset state. 2.1 CTEXT Line This parameter is the CTEXT line changed in the TNC Menu. 2.2 ELMER Flag ELMER is only active in the Packet communications mode, when you are connected. This parameter is the ELMER Flag. If it is a 1 ELMER, is active. IF it is a 0 ELMER is turned off. If the ELMER Configuration File is not present in the default directory, LAN-LINK will turn ELMER off. 2.3 PC Port 4 Custom Address This parameter is the decimal value of the address of your Port 4. Use this parameter if you are using a non standard Serial I/O card. Configure the PC Port to 4. The PC default address for Com4 is 2E8 (hex) or ****. 2.4 PC Port 4 Custom IRQ This parameter is the decimal value of the IRQ of your Port 4. Use this parameter if you are using a non standard Serial I/O card. Configure the PC Port to 4. The PC default IRQ for Com4 is 3. 2.5. VHF Stream switch character This parameter is the VHF Stream switch character. If you wish to change it, you must enter the ASCII representation in this line, and the equivalent stream switch command in the LAN-LINK.SYS file. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 117 2.6 HF Stream switch character This parameter is the HF Stream switch character. If you wish to change it, you must enter the ASCII representation in this line, and the equivalent stream switch command in the LAN-LINK.SYS file. The KAM is currently the only TNC that has different HF and VHF stream switch characters. 24.2.54. TNC Error message This parameter is the error message your TNC generates. The PK-232 generates '?What?', others may generate 'EV?' or '?EH'. 2.7 Connect Timeout Delay This parameter is the time in minutes you stay connected to another packet station after the receipt of the last incoming character. 2.8 ELMER Configuration File This parameter is the name of the default ELMER Configuration file. It is changed through the ELMER Menu. 2.9 Flag XMITOK This parameter is determines if the TNC turns XMITOK on and off when entering and leaving the CW communications Mode. You may have to change this parameter depending on the way you wire the transmitter key plug to the TNC. 2.10 First PacketCluster Command This parameter is the first command (up to 20 characters) LAN-LINK sends to the PacketCluster after receiving a '>' character at the end of line form the PacketCluster. 2.11 Second PacketCluster Command This parameter is the second command (up to 20 characters) LAN-LINK sends to the PacketCluster after receiving a '>' character at the end of line form the PacketCluster. 2.12 TNC Mailbox ON Command This parameter is the command (up to 15 characters) your TNC expects to turn its internal mailbox ON. 2.13 TNC Mailbox OFF Command This parameter is the command (up to 15 characters) your TNC LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 118 expects to turn its internal mailbox OFF. 2.14 VHF Maxframe Command This parameter is the command (up to 15 characters) your TNC expects to set the VHF MAXFRAME parameter. 2.15 HF Maxframe Command This parameter is the command (up to 15 characters) your TNC expects to set the HF MAXFRAME parameter. NOTE: If you are not using a TNC1 you MUST set the HEADERLN parameter to ON. The packet headers and the text of the packets must show up on your screen on separate lines. You must also have the "Echo as Sent" feature set ON ('EAS ON' for PK-232 and 'XM' ON ' for the KAM). 3.0 *.RUN These files contain incoming data from the TNC recorded while the 'capture to disk' function was active. LAN-LINK names them as YYMMDD.RUN automatically (YY = Year, MM = Month, DD = Date, i.e. 900903.RUN is a file for 3 Sept 1990). 4.0 *.DBF (HF.DBF and VHF.DBF) These file contain the log entries. They are Dbase 3 and 4 compatible. The format of the logbook file is the same as that used by the LOGBOOK package of the PC-HAM software package, with more space for comments. 5.0 LAN-LINK.DIR This is the directory file as described in Section 6.1.2. You use it to store connect, NET/ROM, TheLink, KA-Node or digipeat paths as well as name/callsign relationships. Examples are Joe G3ZCZ Alon 4Z4ZB V 4X6AA Milt 4X6AA LR 4X6LR hf-il 4x4hf v 4z4zb 4x4il hf-rj 4x4hf v 4z4zb 4z4rj K1HTV ELK v WB4APR-5! SNJ3! NNJ! WMA! SCCT! K1HTV w9tnn-2 jrw !% w3eax-7 !& w9tnn-2 You create this file with the editor or by using your word processor in its non-document mode. You must leave AT LEAST one space character between the first (key) word and the connect path. When you type in the key word, the program does not care LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 119 about upper or lower case. You may also use the 'reMember Path' option in the Call Menu to make entries in this file. If you already have a YAPP.DIR or a PK232COM.DIR file just rename it to LAN-LINK.DIR and add any NET/ROM and/or KA-Node paths. NOTE: All path entries in LAN-LINK.DIR must be on a single 80 column line. 6.0 CONFIG.SYS You must have a CONFIG.SYS file on the boot disk if you are going to use the disk logging features. This file must contain the line FILES = 20 See the DOS manual for more information about the CONFIG.SYS file. 7.0 *.MBX These are the files associated with the stations you have designated as LAN store and forward mailboxes. Other stations can only :QRU: with you if you have a 'theircall.MBX' file on your disk. Thus if for example you want to use 4Z4ZB as a store and forward mailbox, you will have to create an ASCII file called 4Z4ZB.MBX using Editor, or the non-document mode of your word processor. In this file you will put a list of the call signs of the stations 4Z4ZB can connect to reliably. If for example you want 4Z4ZB to be able to store messages from you to 4X6AA, 4X6LR, G3ZCZ, ON8IK, F0WN,and G8BTB, you would put those call signs in the file, one call on a line as follows. 4X6AA 4X6LR G3ZCZ ON8IK F0WN G8BTB When the QRU function is invoked either by you manually or by 4Z4ZB connecting to you and sending you the command :QRU:, any message files present on your system addressed to any of those stations (E.G. G3ZCZ.OUT and ON8IK.OUT) will be transferred from you to 4Z4ZB just as if you had tried to :QSP: the messages manually or as if G3ZCZ or ON8IK had connected directly to you. The file names on your system will be changed to *.OLD. You must create one file for each designated store and forward station, ie. 4Z4ZB.MBX, G3ZCZ.MBX etc. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 120 8.0 *.BBS These are LOCAL-BBS.BBS AUTO-Upload Command files. Each file is named for the callsign of the BBS that you wish to access. It must have exactly the name as the callsign of the BBS. Thus if the BBS is W9TNN-1 the name of the file must be W9TNN- 1.BBS, or if the BBS is 4Z4ZB then the file must be called 4Z4ZB.BBS. The file must be an ASCII file. that means the word processor must be used in the non- document mode to create it. This file contains the command sequence that you would have typed at the keyboard if you were accessing the BBS manually. The ONE difference is that the text of a message you are uploading with the S command must be followed by the character string :EOF: (on a separate line) as illustrated by the example below. The contents of A TYPICAL *.BBS file are shown below as an example. k 1234 d \net\lan-link.doc s g8btb Test Message This is a test message. :EOF: sp G3ZCZ @ N4QQ Greetings The text of this message is greetings from LAN-LINK. /ex lm r 567 r 593 9.0 LAN-LINK.001 - LAN-LINK.010 These are 10 different ASCII files with fixed names. They can be transmitted using the Alternate function keys. Their contents can be viewed using the Shift function keys. In all cases the function key to use for a particular file corresponds to the number in the file suffix. For example, use Alt/Shift Function Key 3 (Alt-F3) to transmit/view file LAN-LINK.003. You may also use the Edit Menu to edit/create the files. In case you forget what you put in each of the files, LAN- LINK allows you to take a peek into all of them at the same time. Use Control Function key 1 (Control-F1) to look at the first line of all the LAN-LINK.001 - LAN-LINK.010 files and the Brag Tape. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 121 10.0 QBU-RX.BAT This is the command or batch file used in the :QBU: originating station. 11.0 QBU-TX.BAT This is the command or batch file used in the :QBU: receiving station. 12.0 LAN-LINK.QTA You can leave a message on your system for someone else in a file named CALLSIGN.OUT. When the station with that callsign connects to you, the message will be sent, and the filename will be changed from CALLSIGN.OUT to CALLSIGN.OLD. This is fine as long as the path between the stations good. If the path is marginal, it is possible that your station will transmit the message and change the filename, but the link will drop out before the message is received at the other station. If the other station does not connect to you and :QSM:, the message may get lost. If this situation occurs, you can tell LAN-LINK that there is a bad path between you and that station, and not to change the file names without an explicit :QTA: instruction from that other station. You do this by putting the call of the station(s) having a bad path in an ASCII file called LAN-LINK.QTA. Put one call on each line in the form N9BE G8BTB You must use the root call of the station without an SSID. that means, if the station is N9BE-4, just put N9BE in the file. Incoming messages from stations in the LAN-LINK.QTA file will automatically be acknowledged by a :QTA:. 13.0 QZ*.BAT As any LAN-LINK station can either receive or originate a :QZD: and a :QZU: command, LAN-LINK uses four batch files to control Zmodem transfers. These files are as follows. QZU-RX.BAT Batch file implemented after receipt of :QZU: QZU-TX.BAT Batch file implemented after transmission of :QZU: QZD-RX.BAT Batch file implemented after receipt of :QZD: QZD-TX.BAT Batch file implemented after transmission of :QZD: Each LAN-LINK user must configure the QZ*.BAT files for their systems. The port number in the batch file should be set to the PC I/O Port used. The data rate in the batch file should be set to the data rate used between the PC and the TNC, NOT the data LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 1 LAN-LINK 2.00 Disk Files, Page 122 rate used on the radio link. For example, the default QZU-RX.BAT file of 'pcz 1 1200 rz %1' should be changed to 'pcz 2 1200 rz %1' if you are have interfaced your TNC to Port 2 on your PC, and if, the baud rate between the TNC is 2400 baud, the file should be changed to 'pcz 2 2400 rz %1'. Each of the four batch files have to be customized for each user who is not using PC Port Com1 and 1200 baud between the PC and their TNC. The high level of customization required here is because different Zmodem implementations require different sequences of instructions and LAN-LINK does not want to limit you to a specific one. 14.0 ELMER.QSO This is the configuration file for ELMER. The contents of the file are as described in Appendix 8. If this file is not present, you will not be able to turn ELMER on. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 123 APPENDIX 3. Local Area Network Capability VHF Packet radio systems can be considered as part of a Local Area Network (LAN) in which messages can be left by one station in the computer belonging to a second station. At HF the same is true, but the area becomes greater. The basic problem here is that people can only send and receive messages to or from you when you are on-line. To compensate for this, BBS stations were developed which allowed both messages and bulletins to be stored by anyone for later retrieval. LAN-LINK allows you to store messages in your computer so as to use it as an automatic answering machine. By storing the messages in a file called by the name of callsign, with the file extension '.OUT', anyone connecting to the computer will get their message without having to request it. LAN-LINK also extends that concept to cover the eventuality of you wanting to take your computer off-line for some reason. You may now load the message into any other computer you can connect to using elements of the Q code adapted to the High Level Network Communications Language (NC/L) proposed in my book Software for Amateur Radio, (Book number 1560) published by TAB Books, Blue Ridge Summit, Pa. 17214 U.S.A. Unfortunately, while the book is out of print, I do have a few copies left. 1.0 LAN Protocol (G3ZCZ Version) The protocol is as follows. When connected to someone who has their LAN-LINK configured as a host, if you want to store a message you send the following instruction to the other station :QSP: <callsign> where <callsign> is the call of the station that the message is for, not the callsign of the host station in whose computer you are storing the message. [Note use only one space character after the :QSP:]. LAN-LINK sends the :QSP: message automatically using QSP option in the Message Menu. For example if you want to store a message for 4Z4ZB in 4X6AA's computer which is configured as a Store and Forward system, you would first connect to 4X6AA and then send the command as ':QSP: 4Z4ZB'. Better still use :QSP: option in the Lan-Link Menu to automate the sequence. The computer at 4X6AA will respond either with a statement saying that it is ready for you to go ahead, or send a message saying that it can't comply. If it is ready you get a positive reply which will take the form :QRV: <callsign> which if you know the Q code, means " I am ready to accept a message for <callsign>". At this time you may go ahead and send the message. If you type the message at the keyboard, you may use either a control Z (^Z) character or the character sequence :EOF: followed by a carriage return (the ENTER key) to terminate the message. If you have LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 124 first written the message into a text file you may then send it using the 'Send File' option of the Files Menu and the termination sequence is automatic. Once you have completed the message, the other (host) computer will either reply that the message has been successfully stored or give you an error message. If the message is stored and ready to be sent next time the addressee connects to that computer, you will see the message :QSL: on your screen. If something went wrong, you will get back a negative message taking the form :QNO: followed by a number. The number tells you why the operation failed. 2.0 Message Format The message is stored just as if you had left it in your system (except that a header is added identifying the time of reception and the call of the sending station). It will contain a header showing the date and time it was received and your callsign. Should a message for that station already be in the system, yours will be appended to it. In the event the your upload is aborted, the amount of text received before the abort occurred will be stored as the message. When you disconnect from the other LAN-LINK host station, its mail beacon will be updated. Once the message is loaded in the host, it can only be deleted by the operator of the host station. When the addressee connects to the host and receives the message, the file type will change from '.OUT' to '.OLD'. Note QTA stations require positive confirmation of receipt of message for the renaming to take place. 3.0 ASCII File Uploading/Downloading There comes a time when you want to leave a file on your system for someone to download later. You can do this by using NC/L to control the transfer. You must leave the file in a subdirectory defined in the LAN-LINK.SYS FILE called \LAN-LINK\FILES. You must first create it if it does not exist. The station who wants the message just asks for it using :QBM: <filename>, note they do not need to use the full subdirectory path. They must however leave a single space character between :QBM: and the filename. In AMTOR the Mailbox must be turned on for remote functions. For example, you have the latest ARRL DX bulletin, and you want to pass it on. You could pass it to selected people by copying the file to individual messages with the filetype '.OUT', e.g. 4X6AA.OUT, 4Z4ZB.OUT or even G3ZCZ.OUT if you want me to get it, which wastes a lot of disk space. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 125 On the other hand you could tell people that the file was available for downloading, either in the CTEXT connect message line which everyone gets when connecting to you by configuring LAN-LINK accordingly, or in individual ('.OUT') messages. If you include the following in your CTEXT message "ARRLDX.015 now available" people will know that to download it, they just have to type the line ':QBM: ARRLDX.015' (one space character between :QBM: and the file name) to get the file. LAN-LINK is not designed as a BBS, however, if you copy the contents of the \LAN-LINK\FILES subdirectory into a file called DIR (USE DIR > DIR in DOS), anyone can get a list of the files you have stored in it for downloading by typing :QBM: DIR. Since they do not get the real directory, just what was in it at the time you copied it into the file 'DIR', you may keep "hidden" files in this subdirectory. You may thus leave a file for someone to download, tell them that its there by leaving them a message (which they will get automatically when they connect) and no one else connecting will know that it is there. :QDB: allows you to upload text or ASCII files. If you use the 'lan-linK' option of the Packet Terminal Menu, LAN-LINK will automate the QDB and QBM features for you. 4.0 Path Determination to a Dx station If you want to establish a digipeat path to a station somewhat out of your direct range, you need to know which of the stations that you can connect to can hear that desired DX station. If you could get a call monitored (MH list) from the stations that you connect to, you would be able to see if the station you are connected to has heard your desired DX station. LAN-LINK uses the :QMH: command to request such a list. When LAN- LINK receives a :QMH: command, it drops back to the TNC Command Mode and issues a 'MH' command to the TNC (except to a TNC1 which does not support it). It stores the list received in a temporary buffer, and then returns to the Converse Mode and transmits the list back to the station it is linked to. By judicious use of :QMH: you can determine paths to other stations. Note however, that just because one station can hear another station, it does not mean that it can work it. For example, the station you are connected to may be using a power level of 1 watt or so, while the station 200 miles away that it heard was using 100 watts. Test the path yourself, or/and leave a message asking how reliable the connect path between those two LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 126 stations is. If you and a small group use a non standard packet channel for inter-group communications, you may also use the :QMH: function to find out who the station you are connected with, has heard recently, when you first sign on the LAN channel. 5.0 Binary File Transfers In the PC world most binary file transfers seem to be taking place using the YAPP protocol built into the YAPP user terminal program and the BBS software written by Jeff Jacobsen, WA7MBL. As Jeff stated in the documentation, YAPP was written to provide a terminal program for use in testing the WA7MBL BBS code. However for many radio amateurs, YAPP was their first terminal program. The YAPP binary transfer protocol is similar to the Xmodem protocol used on landlines. In order to transmit a file, the sending station breaks the file down into blocks of characters. Each block is transmitted in sequence. After a block has been transmitted, the sending station waits for the receiving station to acknowledge that block and verify that it was received without errors. When two stations are alone on a frequency, they can transfer data quite quickly. So back in 1986 when YAPP was written, it provided the few hams using packet radio with a binary file transfer capability. Today, however, the situation is different. In most urban areas, each packet radio channel is occupied by several stations, and the requirements for speedy binary file transfers are somewhat different. 6.0 Requirements for Transfer Protocols The AX.25 protocol provides for a basic verification that packets have been received error free. Thus if the binary file transfer protocol could start sending blocks, after establishing the connection, then keep sending data until one of three things happen; the link drops out, the receiving station signals that some of the data were received with errors in it, or the whole file is transmitted. If the whole file is transmitted, then the sending station just has to wait for an acknowledgment from the receiving station that the file was received. If the circuit is busy with several stations on the channel, or the path goes through one or more nodes, there will be varying delays in the delivery time of the packets. By not having to acknowledge each block of data in the communications software running in the PC, the file can get through much faster than it would have in the case in which each block has to be transmitted and individually acknowledged. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 127 If the link drops out, it would be nice if the computers, could determine how much of the file was received, then pick up the transmission at that point next time. If the receiving station signals that some data were received in error, the sending station should then begin to retransmit from the start of the error. 7.0 The Zmodem Protocol This situation is not unique to the amateur radio packet network. It is also present in the commercial packet switching environment, and the Zmodem protocol was developed to provide the capabilities described above. Zmodem thus seems to be an almost ideal binary file transfer protocol for use on radio amateur packet channels, and is incorporated in LAN-LINK 2.00. LAN-LINK uses the :QZD: and :QZU: commands to provide the capability to remotely download and upload binary files. :QZD: allows you to download a file from another station, while :QZU: allows you to upload a binary file. :QZD: is configured so that if the link drops outs during the transfer, when the connection is once again established, a subsequent :QZD: for the same filename, will cause the transfer to pick up where it left off when the link dropped out. This feature is not allowed in the upload :QZU: command to inhibit people from injuring files that already exist on the other computer. Each command may be initiated from either end of the link, but to gain the most from the recovery capability, files should be downloaded by the receiving station. 8.0 The PCZ Package LAN-LINK implements the Zmodem protocols using batch files in DOS that call up external programs. This approach allows stations to try different versions of Zmodem and experiment to find the optimal one for their area. LAN-LINK comes with the (PCZ) Public Domain implementation of the Zmodem, Ymodem, Xmodem, Xmodem-1K and Sealink protocols by Drue Kennon and Gary Smith. While each LAN-LINK user can set up binary file transfer batch files to implement any of the protocols, LAN-LINK comes with four default batch files for Zmodem which must be configured by each user as described in Section 24.3. As any LAN-LINK station can either receive or originate a :QZD: and a :QZU: command, LAN-LINK uses four batch files to control Zmodem transfers. These files are as follows. QZU-RX.BAT Batch file implemented after receipt of :QZU: QZU-TX.BAT Batch file implemented after transmission of :QZU: QZD-RX.BAT Batch file implemented after receipt of :QZD: LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 128 QZD-TX.BAT Batch file implemented after transmission of :QZD: Each pair of users can experiment with other protocols and Zmodem implementations using the :QZD: and :QZU: commands after reading the PCZ documentation. The :QBU: command can also be used if the corresponding QBU-RX.BAT and QBU-TX.BAT DOS Batch files are created. LAN-LINK contains an output buffer to store data being output to the TNC. The TNC contains a buffer which stores data about to be sent on the radio link. In the normal course of events, the two buffers fill up so that the Zmodem package used by LAN-LINK may think that all the data has been transmitted, when in fact there are still characters left in the buffers, or the last packet has not yet made it to the destination station. In this case, you may see a message on your screen that the system has sent all the data and is waiting for the final acknowledgment, while at the same time you can see from the LEDs on the TNC that you still have outgoing data in your system. Have patience and wait a while to let the two systems synchronize. In the event that the link is bad and errors occur, this buffering may cause problems which require some of the Zmodem timing parameters to be changed. Should this situation arise, read the Zmodem package documentation. The flexibility offered by the Zmodem protocol has many advantages when used in a packet radio network. LAN-LINK 2.00 implements Zmodem by the use of an external public domain protocol package which provides for the maximum degree of user customization. This capability is provided at the cost of having the individual user customize four batch files using the text editor built into LAN-LINK. 9.0 BASIC NC/L DICTIONARY Messages can be transferred into any other LAN-LINK computer you can connect with using elements of the Q code adapted for the purpose. NC/L command words are summarized in the following paragraphs. There is no command word to request your message. To receive your message, you do nothing, you will receive your mail automatically when connecting/linking with a LAN-LINK station. You cannot normally read messages addressed to another person. 9.1 :QBM: To download an ASCII file, send ':QBM: filename.type'. The filename.type is the file you want. For example ':QBM: dir'. 9.2 :QDB: To upload ASCII files to another LAN-LINK system send LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 129 ':QDB: filename.type'. Files will be uploaded into the same sub-directory as LAN-LINK, and will have a message header inserted at the top of the file to allow the operator to know who uploaded the file. If the operator then wants to make the file available for downloading, he or she can move it to the \LAN-LINK\FILES sub-directory. The '.TYP' following the filename is optional. If you attempt to upload a file which has the same name as one that already exists on the remote system, you will receive an 'error' message. This command is the reverse of :QBM:. 9.3 :QMH: To request a call monitored list ('MH') from the LAN-LINK station that you are connected with, send ':QMH:'. 9.4 :QSM: To request a repeat of a message from a station using LAN- LINK, send ':QSM:'. This command will be valid as long as the host station has not deleted the <yourcall>.OLD file on his disk. If the file does not exist, you will receive a :QNO: 'error' response. 9.5 :QSP: To leave a message, send ':QSP: callsign'. The callsign is that of the station you wish to leave a message for. 9.6 :QRA: When disconnected, to see what stations (using LAN-LINK 1.53+) are on the LAN, or which LAN-LINK stations have messages pending, send ':QRA:'. All LAN-LINK stations will reply with a mail beacon within a few seconds. 9.7 :QRT: To shut down an AMTOR/Packet mode Mailbox/beacon station which is causing QRM, link or connect to the station and send ':QRT:'. 9.8 :QRU: To upload messages from one LAN-LINK/PK232COM (1.38+) system to your computer, send ':QRU:'. You may only use the QRU function with stations designated LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 130 as Store and Forward mailboxes. Put a list of stations that you can connect to reliably in your <callsign>.MBX file and send it to other stations in your LAN also using LAN-LINK. They will then be able to dump their mail messages on you and you on them. If they do the same and send you their file, then you will be able to send messages via them for stations that they can work. While QRU gives you the capability to bulk upload messages to another station in your local area, when you take your machine off line, it may also be used to transfer messages between two LANs via well sighted gateway digipeaters. 9.9 :QNO: ':QNO:' and error message text is a response to a request. 9.10 :QJG: is a response to :QRU: It confirms that the QRU sequence is complete. There are no more messages pending. 9.11 :QRV: callsign is a response to :QSP: callsign. The computer is ready to send the message. End the message with a control Z (^Z) character, or the sequence :EOF: 9.12 :QSL: is a response to a command It confirms receipt of message to that callsign or that a file has been successfully uploaded and stored to disk. It is also used to acknowledge receipt of a ':QRT:' command. 9.14 :QTA: message If LAN-LINK receives :QTA: and a message exists for the connecting station, LAN-LINK will change the filetype from 'OUT' to 'OLD' and respond with a 'QSL'. If a message does not exist, it will respond with a 'QNO'. 9.14 :QTC: message list If LAN-LINK receives :QTC: it will respond with the beacon text showing the mail queue. :QTC: precedes a list of callsigns for whom messages are stored up on a computer. It is used in Packet Beacon transmissions or AMTOR Beacon mode CQ calls. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 3 LAN-LINK 2.00 Local Area Network Capability, Page 131 9.15 :QBU: External Protocols This feature is supplied to allow experimentation with external protocols. 9.16 :QZU: Zmodem Binary File Upload. :QZU: is used to implement an upload of a binary file from another station using an external Zmodem protocol via the QZ*.BAT files. A3.17 :QZD: Zmodem Binary File download. :QZD: is used to implement a remote download of a binary file from another station using an external Zmodem protocol via the QZ*.BAT files. In the event that the link drops out during the transmission, when the link is remade, and the :QZD: retried, the transfer will pick up from the point at which it was interrupted, if the batch files provided are used. PROPOSED EXTENSIONS 9.18 :QYU: YAPP format file upload. 9.19 :QYD: YAPP format file download. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 4 LAN-LINK 2.00, Using other TNCs, Page 132 APPENDIX 4. USING OTHER TNCs The PACKET Mode capabilities can be used on all TNCs. There are minor differences in the command dialogue between different TNCs. The dialogue differences affecting the operation of LAN-LINK are built into the program and set when the TNC type is read from the LAN-LINK.SYS file at the program load time. The non packet modes will obviously result in error messages if attempted on a packet mode only TNC. The following notes apply to different TNCs or digital communications controllers. 1.0 TNC2 (MFJ 1270) The following functions DO NOT WORK because the TNC does not support them. All NON PACKET modes. Software controlled HF/VHF switching. Software controlled baudrate switching. CQ/BEACON Packet terminal mode. TNC Transmit Buffer flush. N2GNJ noticed that he needed 'LC ON' when using a Tiny 2 EPROM Version 2.0 in the MFJ 1270B to make the automatic snatch features work. 2.0 TNC1 (HD-4040) The Packet Communications Mode header colors are not supported in LAN-LINK for this TNC. The following functions DO NOT WORK because the TNC does not support them. All NON PACKET modes. Day/Time functions. 'MH' and remote :QMH: functions. MAIL Packet Terminal Mode. CQ/BEACON Packet Terminal Mode. TNC Transmit Buffer flush. Conference and multiconnect modes. 3.0 Kaypro KPC-2 The Packet Communications Mode header colors are not supported in LAN-LINK for this TNC. The following functions DO NOT WORK because the TNC does not support them. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 4 LAN-LINK 2.00, Using other TNCs, Page 133 All NON PACKET modes. MAIL Packet Terminal Mode. CQ/BEACON Packet Terminal Mode. TNC Transmit Buffer flush. 4.0 KAM LAN-LINK switches colors when it sees the /V or /H following the callsign in the packet header, or in the calls monitored ('MH') list. If you are monitoring both HF and VHF simultaneously, the colors will show you which radio you heard which signal on. If the Mail-Snatch or the QTC-Snatch are triggered, LAN-LINK will change modes and attempt the connect on the correct radio but will not change the band/power information or the logbook to reflect that change in the logbook or in the status window display. Turn the DCD flag OFF for these automatic features to work. The following functions DO NOT WORK because the TNC does not support them. TNC Transmit Buffer flush. The SIGNAL Communications Mode. The Alt-D key in the MORSE Communications Mode. The AMSAT-OSCAR Menu does not allow UoSAT option, as the KAM does not have 1200 baud ASCII capability. 5.0 PK-232 Turn the 'BBS OFF' if you want the Alert Call, packet communications mode header colors and Digipeat Detect features to work otherwise turn it on. 6.0 MFJ 1278 LAN-LINK assumes that the Radio 1 port is connected to the VHF/UHF packet transceiver, and the Radio 2 port is connected to the HF transceiver with the multi mode communications capability. The MFJ1278 suffers from one major deficiency as far as LAN-LINK is concerned. The Echo-As-Sent only works in the AMTOR Communications Mode. That means that you will not see the contents of a file echo in the incoming window as the file is being transmitted in the RTTY mode. The following functions DO NOT WORK because either the TNC does not support them or does not do so in a consistent manner. TNC Transmit Buffer flush. The SIGNAL Communications Mode. The AMSAT-OSCAR Menu does not allow UoSAT option. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 4 LAN-LINK 2.00, Using other TNCs, Page 134 CW Identification. 7.0 Heath HK-21 K3WGF noticed that his Heath HK-21 TNC didn't seem to have the proper circuitry to support true DCD on pin 8 of the RS232 connector. Even though the pin was labeled DCD it didn't signal properly. Set the DCD function in LAN-LINK to OFF to make the Capture-to-Disk close out normally rather than continue to remain engaged. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 5 LAN-LINK 2.00 ANOMALIES and BUGS, Page 135 APPENDIX 5. ANOMALIES and BUGS 1.0 Command/Converse Mode anomalies Since the Program has no way to check the command/converse mode status of the TNC, you may see various Cmd: and error messages from the TNC when using the menus or function key commands. Ignore them for now. If you get an error message, try using the function key again. 2.0 Buffer messages in AMTOR Beacon CQ Mode In the AMTOR Beacon CQ Mode, if the other station drops the link while you are recording the text, BEFORE the callsign has been recognized as a valid callsign, LAN-LINK will time out before logging the QSO and restarting the CQ sequence. If someone else calls in before the time-out has occurred, the text from both stations should be captured to disk, but the log entry may not show both stations, thus the 'LOG' must be compared with the 'RUN' file for QSO purposes. LAN-LINK in the Beacon/Mailbox Mode, normally logs the contact at the end of the line in which it recognized the callsign as a valid callsign. 3.0 FEC +? responses in AMTOR Beacon CQ Mode In the AMTOR Beacon CQ or Mailbox mode, if another station sends a +? in the FEC Mode, the beacon will attempt to send the LAN- LINK.TXT file. The PK-232 however is not in the Converse Mode at that time and will interpret the text of the file as commands. If by some chance, the text corresponds to a valid command the PK- 232 will execute it and put the PK-232 in an unknown state and you may not notice that it did. As such I recommend that the first character of each line in the file LAN-LINK.TXT be a non valid command character such as a number or a period (.) or another punctuation sign. 4.0 Using a monochrome monitor If you are using a monochrome monitor, the text you type into the OUTWINDOW may be fainter than the incoming text. This is because of the default colors used. Change the colors using the Parameter Menu. 5.0 The Packet Conference Mode The Conference Mode has been tested on a PK-232, KAM, a SANYO MBC-675 which has a clock speed of 4.7MHz and other PC clones with faster clock speeds. If you have problems with intermittent selection of I/O channels try slowing down your CPU clock. There is a software delay loop in the program that is used to allow the LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 5 LAN-LINK 2.00 ANOMALIES and BUGS, Page 136 TNC time to switch I/O streams after receipt of the stream change command. This delay is there because LAN-LINK tests for a connect on each channel before outputting any text, so that it does not send un-addressed packets on non connected I/O channels. 6.0 Packet Conference Mode disconnects A Packet conference Mode disconnect returns the TNC to the Command Mode, even if you remain connected to one or more other stations. 7.0 Strange Events If the TNC does not use an interrupt driven serial port you may experience problems when using baud rates greater than 1200. The PK-232 DOES NOT LIKE LAN-LINK to use RS-232 baud rates faster than 2400, and sometimes not even that. Use 1200 until YOU have tested and ARE SURE that a faster one will work. IF YOU HAVE ANY STRANGE PROBLEMs AND ARE USING an RS-232 TERMINAL BAUD RATE to the TNC WHICH IS GREATER THAN 1200, set the Terminal Baud Rate to 1200 and see if the problem goes away. Make sure that your configuration is set the way you think it is. Verify it using the 'display deFault' (and the Misc. Flag if necessary) option(s) in the Parameter Menu. You must have at least one common call or scan word in your SYS file, or you will get errors when you update the SYS file. 8.0 *** DISCONNECTED In the Packet Communications Mode, when you are connected to someone and the TNC sends this text string to the computer, LAN- LINK thinks you have been disconnected and resets. This normally only happens when a true disconnect occurs. However, if the text shows up in the middle of a line being sent to you, it WILL HAVE THE SAME EFFECT AND THINK that YOU HAVE DISCONNECTED if the DCD- Flag is not set in the SYS file, and the TNC does not use the DCD signal on pin 8 of the RS-232 interface. 9.0 *** CONNECTED In the Packet Communications Mode, when you are monitoring traffic on the LAN someone sends this text string, LAN-LINK thinks you have been connected if the DCD-Flag is not set in the SYS file, and the TNC does not use the DCD signal on pin 8 of the RS-232 interface. 10.0 Greek Characters and other garbage in the Incoming Screen. If you see Greek characters in the Incoming screen you probably LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 5 LAN-LINK 2.00 ANOMALIES and BUGS, Page 137 have the wrong parity set in the TNC. first make sure that the RS-232 baud rate is correct. If it is, take the batteries out of it and reset it. If that fails, play with the parity. LAN-LINK sets the serial port as configured in the TNC.SYS file for each TNC. For example, for the PK-232 it is 8 bits, no parity, for the TNC2 it is 7 bits. If you still can't get it to work, set the interface to 7 bits in the configuration file. 11.0 Dumb TNC If the TNC seems to respond to commands but is not sending anything back, you may have one of two problems. You may have a bad RS-232 cable with on wire disconnected. If the computer can operate the TNC in another communications program, try to reset the TNC, take the batteries out, etc. You may also have a not-so- compatible PC. 12.0 Intermittent Lockup Watch out for flow control problems on the cable between the TNC and the PC and between the PC and the Display. Versions of LAN.LINK up to and including 1.55 used software handshaking. Anytime the program received a Control-S (^S) character from the TNC it waited until it subsequently received a Control-Q (^Q). These characters can appear on the LAN in a binary packet, either when binary file transfers are in progress, or in a Inter NET/ROM message. To avoid this lockup, a line containing 'MFILTER 19' was added in the LAN-LINK.SYS file for the PK-232 to make the TNC filter the ^S character out and not pass it to LAN.LINK. LAN-LINK 1.56 and onward use hardware handshaking so this problem should not appear. However if the FLOW and XFLOW parameters are not set to OFF in your TNC, LAN- LINK can appear to lockup. Make sure that they are both set OFF in your TNC. 13.0 Automatic Functions Don't Work This usually happens with the KAM. Set the DCD Flag off, and they should work. Note that in this case the automatic functions don't work. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 6 LAN-LINK 2.00 Update/Revision History, Page 138 APPENDIX 6 UPDATES/REVISION HISTORY 1.58 Default users added. Editor stack/ 1.57 lockout bug and other anomalies fixed, X and Y options added to TNC Menu. O, P, Y and Z options added to Files Menu. Pick option added to message Menu. Com port set up changed. Multi-user operations changed. :QTA: Added. 1.59 F10, First menu character, RTTY/CW file transfer and QBU transparent mode bugs fixed. QTA ack, left/right arrows in log prompt, Local time display, QZU/QZD Zmodem, Metabeacon in packet, MCON control in SAREX Mode, L option in Edit menu, ! in Call menu, K and N in Log Menu, and Z in SAREX Menu added. B removed from call menu. Alt-Y now does RY's in RTTY. XMITOK ON/OFF toggle in PK-232 CW mode. Scrollback not written to capture file. 2.00 ELMER, Alt-W, word wrap, G option in Edit menu, Strswitch chars & error_st in sys file, added. Kam cw/cmd bug fixed, AMTOR sets narrow shift, connect timeout configurable, kam rx/tx inv added, bell filtered out of connectee/log call, kam cw and other parameter changes, log power/band picked up from log, custom word[20] in prompt, Elmer added, event timer 2/6 reset change, mh fire delay for kam, ^T filtered out in all tncs, #T in contest text, NAVTEX and navy mars enabled for kam/mfj, flag_XMITOK added, base count added to SYS file, ctext saved, empty log not read for band/power. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 139 APPENDIX 7 ELMER ELMER: An Expert System Based on a Finite State Machine There are two versions of ELMER supplied with LAN-LINK. One is built in for use in packet mode communications, when connected to someone else. The second version is a stand alone version for use in developing the text files and the logic. The standalone version lets you program and debug your own personal ELMER on your own. The stand alone alone version is a separate product and requires separate registration. Most initial amateur radio contacts (QSO) are somewhat repetitive, in that they send the same information each time. In digital mode communications hams don't type exactly the same information in every QSO, but in general the information exchanged is a subset of a standard set. Hams have noticed this phenomenon and have each created and used files containing standard information. This fact was noticed years ago, and the first so called "bragtapes" were invented to serve that need back when they were using teletypewriters and generated paper tapes for the standard information. ELMER takes that concept a little further and provides expert system. By parsing the incoming text, ELMER will recognize certain words and transmit text files containing replies or further questions, just as if the operator was at the keyboard. Hams can use this feature to build a smart sever they can put on- line on the Local Area Network. The server will prompt people and will serve an educational purpose. ELMER can be set up to teach people about packet radio, license upgrades, or anything else. ELMER can also be programmed to recognize different languages and hold a conversation in those languages. In fact, apart from the dedicated educational and informational server applications, ELMER may be configured with such a variety of vocabulary files so as to pass the Turing test in most typical amateur radio digital mode conversations. 1.0 Introduction ELMER is a program which allows you to build an expert system. It uses the ELMER.QSO file to set up the state machine. The ELMER contains an array of words to be matched, current states, next states and files to be loaded. The ELMER starts up in an initial state. When a line of text is received, it begins to match an array of words against the incoming line of text. It starts matching the words in the order that they are present in the array. It only matches words that are enabled for the current state or for state 0. If it finds a LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 140 match, it advances the next state, and if a valid file name is present (and exists) will output that file. The ELMER will then continue scanning the line of text from the point that the last match was obtained. At the end of the line, it waits for the next line. 1.1 Expert Systems Before discussing ELMER, here's some information about expert systems. An expert system contains knowledge about a particular field to assist human experts or provide information to people who do not have access to an expert in the particular field. It is an information system that can pose and answer questions relating to information borrowed from human experts and stored in the system's knowledge base. Although they vary in design, most expert systems have a user interface, a knowledge base, and an inference engine. 1.2 The User Interface The User Interface to the expert system is the way that the user interacts with the system to extract information from the system. 1.3 The Knowledge Base The Knowledge Base of an expert system contains both declarative and procedural knowledge. The facts describing the situations, events and objects are called declarative knowledge. Procedural knowledge is the information about courses of action and the rules governing the actions. There are various kinds of rules that may be employed. 1.4 The Inference Engine The Inference Engine controls how and when the information in the knowledge base is applied. It determines how the rules in the knowledge base are to be applied to the problem. 1.5 Features of an expert system The following list of features are desirable in any expert system. Useful: The system should meet a specific need. Usable: The system should function so that even a novice computer user finds it simple to use. It should be able to respond to simple questions. Educational: The system should allow non experts to increase LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 141 their expertise. In a similar vein, the system should be able to explain the reasoning behind its advice to allow the user to determine the validity of the advice. Adaptable: The system should be able to learn new knowledge. 1.6 Using an Expert System Expert systems take the form of software packages residing on a hardware platform (computer). The most common use of an expert system is via a man-machine dialogue. The user types something at the keyboard and the system replies. The user interface accepts the input. The input is parsed in some manner, the inference and knowledge engines process the user input in a predetermined manner and an output appears. The parsing function may be a simple pattern matching method commonly called keyword analysis, or a more complicated function using syntactic analysis. Keyword analysis is a logical function in which the presence of various keywords are detected. When a keyword is found, the system responds in the manner in which it has been programmed. For example, if the system detects the words "the wx" in a question, it may respond with " the wx here is sunny". In syntactic analysis, a sentence is analyzed according rules which allow the system to respond differently to keywords which appear in different sequences. For example, the system may respond differently to the question "what is the wx" and "the wx" if it recognizes those words in a sentence. 1.7 The Semantic Network The most general and oldest artificial intelligence scheme for representing knowledge is the semantic network. A semantic network is a collection of objects called nodes. The nodes are connected together by links. Ordinarily, both the links and the nodes are labeled [4]. A drawing of a semantic network contains bubbles to represent the nodes, and lines connecting the nodes to represent the links. Both nodes and links are labeled. The drawing looks just like a PERT or CP/M chart. It is also the drawing used to represent a state machine. 1.8 A State Machine A state machine is a system that exists in several states. The system makes a transition from one state to another as a result of a stimulus. All states and transitions are defined at the time the system is designed. The links in the semantic network are the transitions in the state diagram. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 142 1.9 The User Perception The system appears to be in a rest state. It receives an input from the user and enters a transition to a state in which it processes the data it has just received. After processing the input it generates an output and returns to what seems to be a rest state. In reality, the two rest states (initial and final) are different. 1.10 ELMER ELMER is an expert system for amateur radio. ELMER is based on a finite state machine using table driven software. The declarative knowledge is stored in the form of separate ASCII text and command files. The procedural knowledge is stored in the state table. The Data files in ELMER correspond to the Knowledge Engine (and the Inference Engine), the State Tables correspond to the Inference Engine. ELMER also contains an ASCII editor for text files, and a tool to view the state table. These tools allow the user to "teach" ELMER new knowledge. 1.11 Responses to an Input ELMER has three kinds of reaction to a word match. It can do nothing, output a test file, run a command or overlay a new state table. ELMER's state table contains four entries:- Current State: This is the state that the string match is performed in. ELMER can have up to 63 different states. Next State: This is the state that the ELMER will advance to if a string match is found. Repeat Flag: This is a flag to allow or disallow repeats. If it is a 0 repeats are allowed, if it is a 1, they are not. Command Flag: This is a flag to tell the ELMER how to treat the file. If it is a 0, load a text file; a 2, overlay the current state table with the defined one. Keyword: This is the text string to match in the syntactic analysis of the input text. The text string can be up to 15 characters long and can include spaces. The match is case insensitive, i.e. there is no difference between upper and lower case. Data File: This is a text file to be loaded or a new configuration file. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 143 1.12 Syntactic Analysis ELMER performs syntactic analysis on the input text in the manner described below. ELMER performs a string match on the line of received text against each keyword entry in the state table. ELMER starts with the first entry. If a match is made, ELMER changes state and performs the transient function defined by the Command Flag. All words in the input text including the keyword are then deleted. ELMER then continues the string match until either the input line of text has been reduced to zero length, or, the line of input text has been tested against all keywords in the state table. 1.13 Programming ELMER Programming ELMER is simple. The knowledge base is broken out in terms of states and transitions. States can be passive or active. A passive state is one in which ELMER does nothing other than accept/parse further input. An active state is one in which ELMER loads and displays a text file containing information or shells to DOS and runs an external program. ELMER contains a set of tools for programming and debugging purposes. A state table for the procedural knowledge is drawn up using pencil and paper and a large sheet of graph paper. The built in text editor is then used to enter information into the table. The individual text files containing the knowledge are also created using the editor. The state table viewing tool is used to check the entries. The state table loading capability is used to exercise ELMER and verify the logic. Because the procedural knowledge is contained in the state table, all sorts of rules and linkages may be used. 2.0 The State Table (ELMER.QSO) File These are the contents of the ELMER.QSO file. 2.1 The directory path to the ELMER text files. This item is the directory path to the subdirectory containing the ELMER text files. For example c:\LAN- LINK\ELMER\ or c:\ELMER\ or just c: if you put them in the same subdirectory as ELMER.EXE. If you do use a path you MUST have the last '\' character at the end of the subdirectory name because the program concatenates the directory path to the ELMER. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 144 2.2 The start up file This line is not used in LAN-LINK's ELMER, it is used in the stand alone version. It contains the name of the text file to output the first time ELMER is invoked (if present); 2.3 Window Colors These seven lines, only used in the stand alone version, are the numbers which correspond to the colors of the seven different windows displayed on the screen of the stand alone version, in the following order. Status Window Color: the window at the top of the screen. OutWindow Color : the window in which the replies are displayed. InWindow Color : the window in which your keystrokes are displayed. BottomWindow Color : the bottom line of the screen. Promptwindow Color : the window in which menus are displayed. Option color : the color of the highlights in the menus and prompts. Alarmwindow color : the window in which error and alarm messages are displayed. 2.4 The ELMER initial state. This item is included to allow you to have different state machines, each starting with a different state number. 2.5 State Machine Parameters. The next few lines contain the state machine parameters :- 2.5.1 Current State This is the state that the string match is performed in. LAN- LINK allows up to 63. 2.5.2 Next State This is the state that the ELMER will advance to if a string match is found. 2.5.3 Repeat Flag This is a flag to allow or disallow repeats. 0 repeats are allowed, 1, they are not. 2.5.4 Command Flag This is a flag to tell the ELMER how to treat the file. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 145 0, load a text file, 2, overlay the current state table with the defined one. 2.5.5 Keyword This is the text string to match. It can be up to 15 characters long and can include spaces. The match is case insensitive, i.e. there is no difference between upper and lower case. 2.5.6 Data File This is either a text file to be loaded or a command file to be executed, depending on the state of the Command File Flag. An * character defines a 'do nothing' state in which the Data File is ignored. The two character sequence #1 will cause ELMER to clear the screen before displaying the rest of the text in the data file. 2.5.7 The State Machine File An example of some state machine parameters is shown in this typical extract from an ELMER.QSO file. 1, 2,0,0,what,* 2, 3,0,0,englishman,* 3, 4,0,0,doing,* 4, 1,0,0,country,me-usa.txt 1, 1,1,0,equipment,pk232com.txt 1, 1,0,0,wx,localwx.txt 1, 5,0,0,kenwood,kenwood.txt 5, 1,0,0,811,811.txt 1, 1,0,0,hello,hello.txt 0, 1,0,0,name,joe.txt 0, 1,0,1,hal,hal.bat 0, 1,0,1,log,log11 An * character defines a 'do nothing' state in which the Data File is ignored. 2.5.8 Example of Programming the State Table Consider a typical question that I get asked. "what's an englishman like you doing in this country ?" followed by " The equipment here is ....." Assuming that the ELMER is in state 1, and that the first few lines in the ELMER.QSO file are as shown above. The ELMER recognizes the word 'what' and advances to state 2. Since the LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 146 file name is an '*' character no file is sent. The ELMER then recognizes the word 'englishman' and advances to state 3. The ELMER machine then recognizes the word 'doing' and advances to state 4. The ELMER then recognizes the word 'country' advances to state 1 and transmits the text file 'me-usa.txt', because the Command Flag is a 0. It then recognizes the word 'equipment', remains in state 1 and transmits my bragtape file called pk232com.txt. Since the Repeat Flag is a 1, the ELMER will not retransmit pk232com.txt should it once again recognize the word equipment while in state 1. Since the ELMER scans sections of the line, the same effect will be achieved if the incoming text had looked like :- "what's an englishman like you doing in this country ? The equipment here is ....." Notes: You can only have 63 lines in any one state machine array. You can define up to 64,000 different states. Each state must be an integer. State 0 is a wild card state. This means that any word in the array coded for state 0 will be matched against the incoming text whichever state the machine is in. The entries in the state machine file must end with a line that contains state 666. For example 666, end of file. The number of lines in the array and the current state at the end of each line scanned are shown in the status window. 3.0 The Stand Alone Version Status Window The Status Window provides you with some diagnostic information about the state machine. A typical display is shown below. ╔══════════════ELMER Expert System Demo Version 1.0 (C) Joe Kasser 1991═══════╗ ║C= 1 T= 21 ELMER.QSO ║ ╚═════════════════════════════════════════════════════════════════════════════╝ C= shows the current state. T= shows the number of states (lines) in the state table. ELMER.QSO represents the name of the current state machine. 4.0 The Stand Alone Menu You bring up the menu by touching the 'Esc' character. You are LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 7 LAN-LINK 2.00 Elmer, Page 147 then presented with the following options. ╔══════════MENU══════════╗ ║ F Edit Any File ║ ║ L Load ELMER.QSO ║ ║ P Pick File to edit ║ ║ S Edit ELMER.QSO ║ ║ X eXit to DOS ║ ║ * Show State Table ║ ╚════════════════════════╝ To activate an option touch the highlighted key. 4.1 Edit Any File This option allows you to edit text files. The ELMER contains an ASCII text editor. This editor uses Wordstar compatible commands. 4.2 Load State Table (ELMER.QSO) This option allows you to reload the state table (ELMER.QSO). If a different state table is loaded, its name will appear in the menu. 4.3 Pick File to edit This option allows you to pick a file with the default filetype of 'TXT', and edit it. 4.4 Edit State Table (ELMER.QSO) This option allows you to edit the configuration file. 4.5 eXit to DOS This option allows you to exit to DOS. 4.6 Show State Table This option allows you to see the contents of the state machine. It is used in debugging the logic to ensure that the contents of the table match what you thought you put in. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 148 APPENDIX 8 PCZ Binary file Transfers LAN-LINK uses the PCZ public domain external protocol for binary file transfers by shelling to DOS and executing the QZ*.BAT batch files. The QZ*.BAT files are set up for you by the INSTALL program. This appendix contains the documentation for PCZ as supplied by the developers of PCZ, in case you have problems making binary file transfers work in your system. PCZ - A Public Domain implementation Zmodem, Ymodem, Xmodem, Xmodem-1K, Sealink for the IBM PC family PcConnect Zmodem by Drue Kennon and Gary Smith PCZ is a public domain Zmodem implementation that will allow users of communication software that does not implement internal Zmodem to access it through an external program. It is a full- featured version of Zmodem, but does not have the large volume of bells, whistles & options provided by Omen Tech's DSZ. However, I do believe that it will be suitable for the average demanding BBS'r. PCZ provides support for the basic Xmodem variants: Xmodem, Xmodem-1K, Ymodem & SEAlink. The following is a description of how to start PCZ for file transfers. LEGEND Data enclosed in "[" "]" is optional. Data enclosed in "<" ">" is required. Send Command line: PCZ <1-8> <300-19200> [m] [f] [d] [s] <s?> [r] [@]<filespec> Recv Command line: PCZ <[1-8]> <[300-19200]> [m] [f] [k] [d] [s] <r?> [r] [filespec] Ref: 1-8 - the number 1 - 4, -(8) << PS/2 >> 300-19200 - the number 300, 1200, 2400 etc... m - front-end menu option (see MENU) f - enable FOSSIL comm driver routines k - rx keep aborted received files d - disable video memory writes (use dos) s - request enable Super_Z transfer mode (zmodem only) r?,s? - transfer type sz, rz, sx, rx etc... LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 149 r - resume/recover aborted transfer (zmodem only) @ - command file transfer alert flag (SEAlink, Z,Ymodem) filespec - file name w/extension {complete file spec allowed} {drive:\path\filename.ext} Flags should be placed as shown for standardization purposes. i.e. "f" before "d"; "d" before "k"; "rz,sz" before "r" etc... Due to the nature of the beast, no support is provided for a default port & no default port speed is assumed. NOTE * See environment variables below for more on default port/speed I personally never enter "port" or "speed", but always enter their values. i.e. pcz 1 9600 f sz xxxxxxx.xxx The batch files included reflect this method. "ZMODEM RECEIVE" << SINGLE >> PCZ 1 9600 rz myfile.ext - assume your specified file name. << BATCH >> PCZ 1 2400 rz - Receive ALL sender files. PCZ f d k rz r - Receive ALL sender files assume PCZPORT & PCZSPEED values use FOSSIL routines use standard DOS screen output KEEP all aborted files. RESUME any incomplete previous files. one file mode: PCZ 1 9600 rz INFILE.ARC - Receives one file and names it INFILE.ARC PCZ 1 9600 rz r INFILE.ARC - Recovery effort on file INFILE.ARC NOTE * A word about command line switches might be in order here. The switch flags " f, d, k " are global. That is they control PCZ and not any particular protocol. The "r & s" switch is isolated within zmodem, but is applied to both sender and receiver. If you want PCZ's resume code enabled when sending a LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 150 file then the sender must specify "r" on the command line. Accordingly if the receiver requests resumption of an aborted transfer, the sender must have "r" specified or we won't resume anything. This was requested by BBS Sysops who track download bytes, transfer points etc... Probably so you aren't charged twice or the such like. "ZMODEM SEND" << SINGLE >> PCZ 1 9600 sz OUTFILE.ARC - Send one file to receiver. << BATCH >> Create a TEXT command file with one complete file spec per line, which includes drive and directory information for each file that is not in the directory PCZ was called from. e.g. C:\MYDIR\THISFILE.ZIP There is NO limit to the number is allowed. Have no blank lines in the file. Place the "@" symbol as the first character of the filename. Pass it to PCZ on the command line as follows: PCZ 1 2400 sz @OUTFILE.TXT What you name the command file is your business. It simply must be a standard ASCII file with no software or printer control codes present. An alternative to creating the command file for sending 2 or 3 files may be used. Simply type the file names on the dos command line separating each one with a space. Remember the receiver must be set to accept batch uploads or you might be spinning your wheels. Some BBS packages are just now coming on-line with batch upload features using PCZ. They normally indicate (BATCH) if it is supported. BBS << BATCH >> One method for implementing batch uploads on a bbs is to use the log file and examine the transfer status character. The first character of each line in the log file denotes how the transfer finished. A "1" for good transfer & "0" for a failed transfer. Armed with this information, simply setup to call PCZ in batch receive mode. After PCZ has finished and your bbs code has control. Open the logfile and read in the line(s) of LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 151 information. You may now format a string to send the user about the status of each file he/she sent, prompt for a file description etc.. After you have dealt with each entry in the logfile, simply close the file and delete it. PCZ will create a new file for the next transfer session. If you desire a continuous record of the transfers then you should create your own and append each entry you read from the pczlog to your continuous log file. The information below shows exact start positions for each piece of data. The x's denote the length of each element, the first (x) shows start position as PCZ will write it to the log. e.g. Below, the file size is 47877. PCZ will always write the file size as a 7 character string which begins at position 21 in the line. Hence, read from pos(21) to pos(27), trim any blanks & convert to decimal value etc.. Log extract w/char positions: 1 2 3 4 5 1234567890123456789012345678901234567890123456789012345 x xx xxxxxxxxxxxx xxxxxxx xxxxxx xxxx x 1 sz PCZ40x.ZIP 47877 @ 2400 bps @ 237 cps 0 6 7 8 6789012345678901234567890 xxxxxxxxxxxxx errors Fri 10/5/1990 "XMODEM VARIANTS" To receive files using any of the Xmodem variants, the format is: PCZ <port> <speed> rs filename - SEAlink receive PCZ <port> <speed> rs - SEAlink Batch receive PCZ <port> <speed> rx filename - Xmodem receive PCZ <port> <speed> r1 filename - Xmodem-1K receive PCZ <port> <speed> ry filename - Ymodem receive PCZ <port> <speed> ry - Ymodem Batch receive Remember the "k" options works for all of the receive modes. Hence you can receive a file via SEAlink, have it abort on errors, and then later RESUME the transfer using Zmodem. To send files using any of the Xmodem variants, the format is: PCZ <port> <speed> sx filename - Xmodem PCZ <port> <speed> s1 filename - Xmodem-1K PCZ <port> <speed> sy filename - Ymodem * LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 152 PCZ <port> <speed> ss filename - SEAlink * * Refer to Zmodem Batch sending for batch transfers via Ymodem and SEAlink NOTE: The bytes and cps rate reflect the actual number of bytes sent to, or received from the IOBuffer as a transfer progresses. It does not necessarily reflect any specific "BLOCKSIZE". When sending, as a transfer nears it's end, you will see the cps decline. That's because PCZ uses buffered output vs a simple "sector size" buffer. This will let you see actually how PCZ is progressing in the transmission of data. In the best case "Full Streaming Zmodem", you will see the time for actual file data; worse case time will reflect the transmission of data headers and block acks. It is different, but I hope everyone can appreciate a more accurate account of what is happening inside the powerful zmodem protocol. ** : The "Transfer Time" reflects PORT speed, (NOT MODEM) speed! If speed conversion is being used, FORGET the transfer time. "ENVIRONMENT VARIABLES" PCZ supports several environment variables which can make setting up a comm pkg. or BBS more "user friendly". These variables are as follows and should be placed in the autoexec.bat file as I have them shown here or modify the setenv.bat file included to accommodate your system. "DRIVE" refers to the letters "A".."Z" "YOURDIR" refers to a complete directory specification. i.e. \COMM\ARC\ "YOUR.FIL" refers to a filename with extension that you want PCZ to use vs it's default name. "DIRRX" set DIRRX=drive:\yourdir\ This variable provides the ability for all your received files to be placed in a single location. It is very useful for bbs purposes as well as general comm program usage. If you specify a directory spec on the command line, it will override DIRRX. Therefore you can easily set the variable and then just forget about it. If DIRRX isn't set and no spec. is given on the command line, your receive file will be created in the current active dos directory. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 153 "PCZLOG" set PCZLOG=DRIVE:\YOURDIR\ In the log file's case, it specifies the directory you want your PCZ.LOG file to be kept in. If "PCZLOG" is not found in the environment then no log file is generated. set PCZLOG=DRIVE:\YOURDIR\YOUR.FIL As an option to the log file name "PCZ.LOG" you may specify your own filename in the filespec. This provides greater flexibility with some bbs packages such as RBBS which expects it's own naming convention to be used, and for multitasking environments etc... If your "YOUR.FIL" exist, it overrides filename "PCZ.LOG" in all cases. "PCZPORT" set PCZPORT=(1-8) PCZ will use the port number (1-8) as the default port. "PCZSPEED" set PCZSPEED=(300-19200) PCZ will use the speed (300-19200) as the default speed. NOTE ** If you specify the PORT or SPEED on the command line, it will override a default set by the environment variables. "PCZDIR" set PCZDIR=DRIVE:\YOURDIR\ If you experience any problems with PCZ not being able to access it's overlay file. Setting this variable will cure the problem. DRIVE:\YOURDIR\ should point to the directory where you have located PCZ.EXE IMPORTANT NOTE: NO SPACES are allowed when setting an environment variable! i.e. {WRONG} set PCZLOG = C:\COMM\ will not work. That's not my fault. It is just DOS.... i.e. {ahhhh} set PCZLOG=C:\COMM\ LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 154 "PORT & IRQ" It has seemingly become necessary, instead of interrupt sharing, to reassign Comm. PORT addresses and use seldom triggered IRQ lines e.g. "5 & 7" to allow multiple 'more than two' ports on one machine. Efforts to support this trend have been successful with PCZ. Referring back to our PCZPORT environment variable: set PCZPORT=1 If you have reassigned you IO card addresses etc..., you can force PCZ to comply with your wishes. Lets say you want to use PORT 3 @ 2E8h on irq 5. You set PCZPORT in this manner. set PCZPORT=3,2E8,5 | | | | | |____ IRQ line number | |_______ PORT address |__________ PORT number If you specify an invalid address or one you card isn't set for then PCZ will simply abort during it's port validation routine. This method should provide the support needed for those who like to match their wits against the cpu's. "Super_Z" (tm) Always in search for faster from fast. Super_Z takes zmodem to the ragged edge! If you are one of the blessed, and enjoy relatively noise free transmission lines, you should see an increase of 2 to 3 percent efficiency. XON/XOFF MUST be disabled and the modem must pass these characters. You may activate Super_Z via the command line switch "s". As is usually the case, Super_Z can be called by the receiver or by the sender. That is to say, that either can flag for Super_Z and if the remote version supports Super_Z, we're doing it. Regarding noise, a seldom thought of fact is that just because you local transmission lines are great to one place, someone else's local lines may be the pits. A good example is.... When I log on to the "Corner" from Texas on a "596" extension I rarely every get a line hit. When I use the "995" extensions I am prone to hits anytime. A reverse situation might occur in your particular area. It simply depends on the quality of any of the many exchanges you might encounter. I can only hope you are one of the lucky ones. "NETWORK SUPPORT" PCZ has been tested completely in a network environment. It will LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 155 allow multiple users to read the same file via use of DOS's shareable attribute. It will also lock any files that it is currently writing to. This has been tested using Novell Netware, LAN Manager, and CBIS Network-OS. "MENU FRONTEND" Many fine programs exist which allow protocol engines to be called from a communications package. In an effort to make PCZ all the more user friendly, there is now a simple menu system built into the program. It is controlled by the file PCZ.CFG which is included in this zip file. Take a few moments to read over it. It may be that it is just what you are looking for in the way of a nice user interface. The design and layout of the system is very simple and straight forward. You control the options and protocols you wish to have active. PCZ.CFG comments explain the various functions you can use. To use the menu system simply call PCZ in the following manner. PCZ m Make your menu selections and complete the command line with your filespecs. "FOSSIL SUPPORT" FOSSIL is an acronym for "Fido/Opus/SEAdog Standard Interface Layer". This version of PCZ implements the use of FOSSIL communications support. To date only one, "X00.SYS" driver has been tested to work with PCZ. X00.SYS is a product of Raymond Gwinn. It has proven itself in many environments and I recommend it to you without reservation. X00.SYS was chosen because it provides "FIFO" etc... support for the 16550 UART chip. My internal routines support the chip but not all it's features. Also X00.SYS provides enhanced ability to work in a multitasking environment such as DeskView. If DeskView is active PCZ gives idle processor time back to the cpu for smoother operations. For a brief description of setting up X00.SYS on your system read the enclosed file PCZFOSSL.DOC Making use of the driver with PCZ is as simple as adding "f" to the command line. It should be placed after the baudrate in all transfer types. i.e. PCZ 1 9600 f sz OUTFILE.ZIP When PCZ starts, it will check for the presence of the driver in memory. If it is resident all will proceed as planned. If however, the driver is not in memory, PCZ will gracefully shut down with a message stating this fact. I gave careful thought to jumping to the internal routines, but decided against it for a LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 156 couple of reasons. In some cases the ports may be scrambled which will surely cause a system lockup on PCZ's part. A problem may exist with the driver you are using, giving false info which PCZ's routines would not like very much. A "dumb" terminal might have charge of things and not want another routine hanging around, etc... "PHONE SUPPORT" Phone support can be provided when you require it, if you call while I am home. I umpire for our local women's softball league on Mon. & Tues. nights. I play golf on Wed. & Thurs. evenings. Fri. night I do what Maureen tells me to do! Sat. is up for grabs and Sun. morn & evenings I am in church. Please try me sometime other than those mentioned ...... Seriously though, any night (late) will be fine. Just try and make it before 10p.m. CST if possible. Note from the author: Over the last year PCZ has received some very good reviews. More users rely on the program for their transfers now than I thought would ever be interested. For this I am especially grateful and would thank each one if possible. Gary & I will continue to grow with the needs of the BBS community. We ask for your continued input and support, with our assurance that your IDEAS, "cheers & jeers" are taken with sincerity. Thanks Drue History ------- V1.01.88 - Initial release, no known bugs. Please report any problems to Drue Kennon. V2.01.89 - Extended version that contains Xmodem, Xmodem-1K, Sealink, and Ymodem Batch in addition to Zmodem. Also provides full file sharing for use in networking environments. V2.11.89 - Fixed several reported bugs. Enabled hardware flow control for use with MNP type modems. Enhanced port speeds up to 19.2k, and tightened some code for more efficient operation. Properly set errorlevel 1 in event of transfer failure. V3.03.90 - Fixed a problem with SEAlink xfers not seeing the last EOT. Batch sending for SEAlink per request. Enhanced some screen data writes. V3.06.90 - Fixed a problem with SEAlink xfers created by making the last fix. Zmodem command file name can't be fouled due to misunderstanding the docs. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 157 NOTE: Unless forced into it by the users, I do not plan to support 7 bit data transfers. Nor can I figure why any IBM machined BBS would? Did I miss something along the way? V3.08.90 - Got with the program and added support for FOSSIL driver. e.g. Gwinn's Communications Controller, X00.SYS add "f" to cmd line params for fossil). Removed internal support for default port and speed which caused problems for multitaskers. Defaults are now specified through environment variables. Added environment variable for default receive dir. Reinstated environment variable for pcz log file. V3.09.90 - By popular demand, namely "Gary", I added yet another multitasker enhancement. Since the cpu is much faster than the port, idle time occurs during output. This time is now "given back" to the cpu, allowing the "other side" to operate smoother and more efficiently. V3.10.90 - Some users mentioned that PCZ would wait forever in a transfer if the carrier was lost. I couldn't dupe the problem, but added several more checks nonetheless. The logfile has changed so that you may specify a full filespec. including filename for you logfile in the env. var. The first char of each line in the file represents pass or fail. "0" = failed xfer "1" = good xfer. Keep those cards and letters coming! V3.11.90 - ArrrrG! %#^^#%%@#*$(%*#$%($$%&*( the &*&^*&^ woes of changes really &#$^& my &(&^#$. V3.12.90 - Forget 3.11.90 ever existed! Several routines got a face lift! You should see more efficiency with this release. I can't begin to go through the entire chase with you here, but I need a new can of RAID! Seems there is never a total end with a bug problem, in programming as well as the home! I must offer a special word of thanks to Dick Melville from San Marino for his the help with RBBS interface problems. Dick was an excellent BETA Buster! And to Steve Clancy who finally helped me see there was NO carrier on the line! V4.00.90 - {BETA} Version 4.00 represents a major revision change to PCZ. As you have noticed, if you've used prior versions, there are two PCZ files now instead of one. PCZ.EXE is the global executable file and PCZ.OVR contains the actual protocol functions. The decision to go with overlay functions was made due to the fact that more Sysops are using PCZ with their BBS's in a multitasking environment. Memory usage has been drastically reduced. Additionally, each transfer type function i.e. "sz,sx(1),ss,sy" & "rz,rx(1),rs,ry" is totally self contained which simply means once the program loads and a transfer type is called, no other overlay read is needed. The LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 158 function completes and exits. Simply put; execution time has been enhanced. V4.01.90 - {BETA} Dick & Steve V4.02.90 - {BETA} Dick & Steve V4.03.90 - {BETA} PcConnect, Dick & Steve V4.04.90 - {BETA} PcConnect V4.05.90 - Major revision V4.xx.90 released on the world! V4.06.90 - Some enhancements added here include; Super_Z(tm) by PC², offers enhanced transfer times when used with error correcting modems and relatively noise free transmission lines. No limit to the number of files allowed in a batch transfer command file. Non-standard PORT, IRQ line assignments supported via environment setup. Frontend menu system for comm package use. PCZ is supplied as a '.EXE' file which when executed breaks it's code out into overlays. The largest executable code segment will run well inside of a 64k memory segment. Personal contact may be made by one of the following methods. Drue Kennon Gary J. Smith Rural Route #2 Box 54 6122 Cedar Wood Drive Center, TX. 75935 Columbia, MD 21044 Voice 409-598-3809 The Programmer's Corner Home of "PcConnect" & "PCZ" Data/BBS: 301-596-1180 Data/BBS: 301-995-3744 Data/BBS: 301-621-4636 10 roll over lines in place with over 1.5 gigabytes of storage space DSZ, ZCOMM, Professional-YAM are Copyrights of Omen Technology Inc, all rights reserved. X00.SYS Copyright (c) by Raymond L. Gwinn, All Rights Reserved. PCZ Copyright (c) by Drue Kennon, All Rights Reserved. Super_Z(tm) is a trademark of PC² ** If you are the author of a communications package that has zmodem implemented internally and would like to enable Super_Z in you program for PCZ compatibility, look over SuperZ.Doc. If you have any questions or problems then just drop me a line or call and we will be glad to help you out. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 159 The PCZ Menu Transfer System This is the PCZ.CFG file. ;To make use of this transfer menu system PCZ should be called in the following manner. ;PCZ m <ENTER> ;We assume in this config file that you are using SETENV.BAT to preset your PCZ parameters for PORT and SPEED. If this isn't the case then simply add them on the protocol lines below in their proper place. You should be able to see from the listings the format used here. i.e. ;SEND without the ';' begins send protocol block ;END without the ';' end the protocol block ;The protocol goes on a line followed by the ':' char followed by PCZ's command line options for that protocol. You will be prompted to complete the command line with your filespec(s) once the program is started etc... pretty simple huh? ;Simple yes! but simple minded as well, and if you fail to follow these guidelines.... who knows what type of protocol you might be trying to use for a transfer. Just to satisfy your cats curiosity you may uncomment the first line after SEND. Run PCZ using 'm' menu option, select upload and see what happens. No your pc won't bark but it might barf if you select 'A' as your protocol type. ;The following represent the send parameters. Using the ';' at the beginning on a line comment out any protocol you do not wish to use during you file transfer sessions. SEND ;flag for beginning of send protocols ;TOSSIT: sp ;This is a curiosity test line ;XMODEM: sx ;send a file using xmodem ;X1K: s1 ;send a file using xmodem 1k blocks ;YMODEM: sy ;send a file using ymodem with file header information ZMODEM: s sz ;send a file using Super_Z zmodem LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 8 PCZ 4.06.90 Nov. 27, 1990 Page 160 SEALINK: ss ;send a file using sealink END ;end of send protocols :The following represent the receive parameters. RECEIVE ;flag for beginning of receive protocols ;XMODEM: rx ;recv a file using xmodem ;X1K: r1 ;recv a file using xmodem 1k blocks ;YMODEM: ry ;recv a file using ymodem with file header information ZMODEM: s rz ;recv a file using Super_Z zmodem SEALINK: rs ;recv a file using sealink END ;end of receive protocols ;You may add any of the other command line switches you wish to the above. They are ; 'f' use FOSSIL ; 'd' no direct screen writes ; 'k' keep all aborted downloads ;Thanks and have fun! LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 9 Other PC Software by Joe Kasser G3ZCZ,Page 161 APPENDIX 9 Other PC Software by Joe Kasser G3ZCZ 1.0 PC-HAM 3.52 BY G3ZCZ LOGBOOK Full blown logging package. With automatic check of logs for awards such as DXCC. Allows you to recall any entry by call sign within seconds. Indexed displays, QSL'ing, Contest mode QSL'ing (prints the lot) and lots more. Although written in dBASE3 the package contains a compiled version (LOGBOOK.EXE), so you don't need dBASE to run it. The source code is ONLY given to registered users. It can convert your exported LAN-LINK.LOG file to LAN- LINK.DBF to put this package to work. Ideal for DX-peditions or for DX robot users to handle QSLing and log statistics. CONTEST Keeps Dupes in memory, logs QSO's to disk in format which can be processed by the LOGBOOK package. Now compiled in Turbo BASIC, source code is supplied so that you can modify the program to meet your requirements. CQSS Sweepstakes game compiled in Turbo BASIC. Work the ARRL Sweepstakes contest on your computer. You are located just outside Washington DC. A propagation model is built in to the program. This program is REQUIRED training for all sweepstakes operators. Earlier version of the program is described in detail in 'Software for Amateur Radio' by Joe Kasser G3ZCZ, published by TAB Books, Blue Ridge Summit, PA. 17214. WHATSON Predict HF Propagation for given days. Contest mode with printout to whole world at hourly intervals. Needs BASIC. 2.0 STARTREK The Computer Program An ideal task for the beginner to learn a language on is a simulation game which is written around the computer that the beginner has available. For in that case, there is complete control of all inputs and outputs, This kind of game in which the player makes decisions based on the information available to him or her available at the time), can be made sufficiently sophisticated and complex so as to make writing it an adequate challenge for anybody. The techniques used in writing a good game are the same that programmers use in professional activities. Writing a good game poses a challenge that allows you to develop good habits and LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 9 Other PC Software by Joe Kasser G3ZCZ,Page 162 techniques for programming and also allows you to learn a language in an interesting manner. By taking an orderly approach to the game design, complex operations may be clearly understood and converted to computer code with the aid of a language reference manual, irrespective of the language being used. This product teaches the techniques for writing such a game using the STARTREK game as an example, and the BASIC language as the programming language in which to write the code. Registration fees. Single Copy $15.00 10 - 50 Copies $12.00 per registered copy. 50 - 100 Copies $10.00 per registered copy. 100 + Copies $8.00 per registered copy. 3.0 WHATS-UP 1.20 WHATS-UP is a tool for experimenting with orbital dynamics and Telemetry Decoding and display Program for the UoSAT-OSCAR 11, AMSAT-OSCAR 13, Fuji-OSCAR 20 and the AMSAT Microsat Spacecraft (OSCARs 16, 17, 18 and 19). It is table driven via the configuration files to allow maximum flexibility. WHATS-UP contains the following features: * Can automatically set Kenwood Radios to spacecraft beacon frequency when satellite comes over your horizon. * Can automatically read the frequency from Kenwood Radios to a disk file for Doppler frequency measurements. * Can automatically configure a PK-232 for each spacecraft data format. * Reads 2 Line and AMSAT format orbit element data files. * Provides antenna azimuth and elevation pointing data. * Real time, Playback and Dumb Terminal mode. * Automatic Capture-to-disk of raw telemetry. * Extracts telemetry channel data to a database or spreadsheet readable file for further analysis. * Link quality measurement on packet telemetry. * Capability to print the raw telemetry as it is received. * Up to 16 user configurable display pages (screens). You set the position on the page (width of engineering unit field, and number of decimal places) that a parameter is displayed at. * Wild card page (parameter shows up on all pages). * Selectable display of Engineering units or raw byte for each display page. * Display of raw packets (i.e. STATUS) * Color changes if a parameter value changed between successive frames. * Audio and visual alarms if a telemetry value exceeds, falls below or falls outside a preset limit value(s). LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 9 Other PC Software by Joe Kasser G3ZCZ,Page 163 * Dumb split screen terminal mode (a la LAN-LINK). * Customizable colors, PC to TNC baud rate, data parity and stop bits. * Default spacecraft configuration files. * Time of day clock display (in HH:MM:SS format) Real time analysis requires a receiver and demodulator. Analysis of playback data can be performed with just the computer and WHATS-UP. If you would like a copy of WHATS-UP and have captured any telemetry to disk, especially daytime or southern hemisphere passes, please put them on a disk and send it in with your request, a mailer and return postage. Don't let the individual data files become too long. I suggest that you rename them every day in the format YYMMDD.SC, such as 900824.D17, 900824.F20, etc. IF YOU ARE INTERESTED IN OSCAR AND SPACECRAFT TELEMETRY, THEN THIS PROGRAM IS A MUST. 4.0 ELMER 1.00 ELMER is an Expert System Based on a Finite State Machine. There are two versions of ELMER supplied with LAN-LINK. One is built in for use in packet mode communications, when connected to someone else. The second version is a stand alone version for use in developing the text files and the logic. The standalone version lets you program and debug your own personal ELMER on your own. The stand alone alone version is a separate product and requires separate registration. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 10 How Shareware Works,Page 164 APPENDIX 10 How Shareware Works The Association of Shareware Professionals (ASP) has established standards for its members and for any organization which has "ASP Approved" status. The ASP wants to make sure the shareware principle works for you. If you are unable to resolve a problem with an ASP member or organization (other than technical support), the ASP may be able to help. Please write to The ASP Ombudsman, 545 Grover road, Muskegon, MI. 49442-9427, USA. You are encouraged to copy the floppy disk and share it freely with others. You have the luxury of trying out the product at your own pace and in the comfort of your own home or workplace. After you have used the material for a reasonable evaluation period (30 days), you should either discontinue use of the material or register your copy. Your support is important and greatly appreciated. With it, Shareware authors are encouraged to design and distribute new products. Without it, a great deal of high quality, low cost software will cease to be available. Why pay at all? * You receive support from the author. * You receive a CURRENT copy of the program. * Your input and ideas help shape future products. * A sense of pride and ownership in having honestly participated in the Shareware revolution. * You help to keep software prices down by supporting a distribution method which doesn't depend on expensive advertising campaigns. Be aware of the following restrictions, designed to protect the community of Shareware users and to prevent greedy people from taking unfair advantage of the trust, hard work and good will of Shareware authors. 1. No price or consideration may be charged for the material. However, a distribution cost may be charged for the cost of the diskettes, shipping and handling, not to exceed $6. 2. The files and programs on the disks may not be modified or deleted. 3. The material cannot be sold as part of some other more inclusive package. 4. The material cannot be "rented" or "leased" to others. 5. The end user must be told clearly in writing on the outside of LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 Appendix 10 How Shareware Works,Page 165 the package and in all advertising that the diskette(s) are "Shareware." 6. The package must contain a written explanation that the disk is for evaluation purposes, and that an additional "registration fee" is expected by the author, if the material is used beyond an initial evaluation period. 7. In the case of distribution via any telecommunications link, the following must be done: An error checking protocol must be used. The individual files must be combined into, and transferred in a library or archive format. 8. Shareware distribution is permitted only in the United States, Canada, England, and Australia. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM, Page 166 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM To: Joe Kasser G3ZCZ, P.O. BOX 3419, SILVER SPRING, MD 20918. CALL ________________ TODAY'S DATE _____________ NAME ______________________________________________ ADDRESS ___________________________________________ ___________________________________________________ CITY ___________________________________________ STATE _________ POSTCODE ____________ TELEPHONE ____________ TNC TYPE _________ FIRMWARE REV __________ HOME BBS ___________ DISK SIZE 5.25 _____ 3.5 ____ Please register me as a user of LAN-LINK. I am currently using LAN-LINK Version ______ which I obtained from __________________. Please send me the latest version of LAN-LINK or if a more recent one does not exist at this time, QSL my registration and add my name to the list to receive a free update when it becomes available. I would also like to order a copy of your book "Basic Packet Radio" which explains how to get the most out of packet radio and includes a printed LAN-LINK Manual. I also enclose an additional amount for evaluation copies of ELMER -, WHATS-UP _, PC-HAM _ and Startrek TCP _ ($5 for 1 program, $10.00 for the set). If I like them, I plan to register them in due course. LAN-LINK Registration ($45.00) __.__ ELMER Registration ($45.00) __.__ Basic Packet Radio ($29.95) __.__ Evaluation software $ __.__ ____________________________________ Total Enclosed $ __.__ Signature ____________ My favorite operating modes are ______________________________. Additional Features I'd like to see in future releases of LAN- LINK. Keep Conference Bridge Up __ YAPP Binary File compatibility __ Expanded Contest Operation __ More AMTOR (explain below) __ NTS capability __ Picture Transfer capability __ Telephone Modem capability __ PacketCluster Menu (Like BBS) __ Kenwood Radio Control Menu __ Dumb Terminal (CP-1, ST-5 etc.) Baudot/ASCII RTTY operation __ NOTE: some additions come into LAN-LINK as a result of user suggestions, so here's your chance to get some input in. Comments, likes, dislikes, wish list, etc. (on back of page) LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM, Page 167 APPENDIX 12 LAN-LINK PROBLEM REPORT Name ______________________________________ CALL _______________ Street __________________________________________________________ City _______________________________ State _____ ZIP __________ Tel. ____________________ LAN-LINK version ____ 1. Describe your computer system. Manufacturer ____________________ Model ___________TNC __________ Firmware _____ DOS Version ________________ Clock Frequency _________ MHz. List peripheral equipment and cards installed in your computer. Video Herc/EGA/CGA_____ _______________________ _______________________ _______________________ _______________________ _______________________ What memory resident programs were installed when the problem occurred? _______________________ _______________________ _______________________ _______________________ 2. Describe the problem in detail. What were the Misc. flag state-sequence numbers when the problem was happening? 3. Describe the sequence of events or keystrokes that led to the problem. 4. Any other information that may help in locating the problem. Use additional sheets of paper if necessary. ATTACH a copy of your LAN-LINK.SYS file. Mail to: Joe Kasser, P O Box 3419, Silver Spring, MD. 20918. LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM, Page 168 APPENDIX 13 LAN-LINK Index of Words, Page # Abort, 36, 124, 151, 154 Access, 1, 13, 18, 52, 120, 140, 148, 153 ACHG, 8, 106 Alarm, 4, 34, 35, 42, 53, 54, 94, 107, 144 Alarmwindow, 94, 144 Alert, 2, 3, 13, 26, 27, 28, 34, 41, 42, 72, 79, 95, 133, 149 ALFD, 98 ALIST, 7, 99, 100 ALISTEN, 8, 106, 107 Alt-A, 2, 4, 28, 62, 65 Alt-B, 2, 28, 72 Alt-C, 2, 18, 26, 28, 104 Alt-D, 2, 28, 52, 80, 100, 111, 133 Alt-E, 2, 4, 26, 28, 63, 65 Alt-F, 2, 4, 28, 36, 63, 65, 120 Alt-J, 2, 28 Alt-K, 2, 29 Alt-L, 2, 29, 83 Alt-M, 2, 23, 29, 81 Alt-N, 2, 29, 103 Alt-O, 2, 29, 74, 83 Alt-P, 2, 29 Alt-Q, 2, 30, 39 Alt-R, 2, 30, 45 Alt-S, 2, 4, 30, 63, 82 Alt-U, 4, 63 Alt-W, 2, 30, 60, 138 Alt-X, 2, 17, 18, 30, 66 Alt-Y, 2, 30, 138 Alt-Z, 2, 5, 30, 46, 63 AMTOR, 2, 3, 7, 8, 9, 11, 12, 14, 21, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 34, 35, 36, 37, 41, 42, 43, 44, 45, 54, 59, 61, 62, 78, 79, 83, 86, 92, 95, 99, 100, 106, 107, 124, 129, 130, 133, 135, 138, 166 AMTOR-FEC, 24 Annunciator, 2, 13, 21 ANOMALIES, 9, 135, 138 APLINK, 42, 92 ARQ, 2, 3, 8, 27, 28, 34, 42, 43, 100, 106, 107 ASCII, 4, 5, 7, 8, 9, 11, 12, 13, 15, 19, 22, 24, 27, 31, 32, 48, 56, 58, 59, 71, 72, 99, 110, 116, 117, 119, 120, 121, 124, 125, 128, 133, 142, 147, 150, 166 ASP, 164 Attempt, 22, 34, 41, 42, 43, 48, 54, 60, 80, 84, 129, 133, 135 Auto, 3, 34, 38, 39, 41, 42, 45 AUTO-Upload, 120 AUTOCQ, 21, 24 Automatic, 6, 10, 12, 13, 14, 15, 20, 22, 23, 26, 29, 35, 36, 38, 46, 54, 61, 73, 77, 78, 83, 84, 98, 106, 109, 111, 123, 124, 132, 133, 137, 161, 162 LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM, Page 169 Batteries, 17, 69, 137 BAUDOT, 7, 8, 11, 12, 15, 24, 27, 31, 32, 68, 69, 72, 98, 99, 108, 166 BBS, 1, 2, 3, 4, 5, 6, 7, 8, 13, 15, 16, 18, 20, 23, 27, 30, 32, 38, 40, 41, 42, 44, 46, 47, 48, 51, 52, 53, 54, 67, 70, 71, 73, 76, 77, 84, 85, 86, 90, 91, 92, 97, 98, 102, 114, 115, 120, 123, 125, 126, 133, 150, 152, 153, 156, 157, 158, 166 Beacon, 2, 3, 5, 6, 7, 9, 12, 13, 14, 16, 21, 22, 23, 25, 35, 41, 42, 46, 47, 48, 52, 61, 62, 71, 72, 75, 76, 77, 78, 79, 80, 81, 84, 85, 92, 98, 101, 105, 107, 115, 124, 129, 130, 132, 133, 135, 162 Bell, 55, 71, 138 Blink, 35, 73 BottomWindow, 94, 144 Bragtape, 146 BTEXT, 21, 80 Buffer, 2, 3, 5, 9, 12, 27, 28, 31, 35, 36, 40, 55, 68, 69, 78, 90, 104, 125, 128, 132, 133, 135, 152 BUGS, 9, 135, 138, 156 Bulletin, 6, 16, 24, 71, 85, 97, 115, 124 Bulletins, 13, 20, 51, 71, 85, 97, 102, 123 Capture-to-Disk, 4, 5, 6, 20, 23, 24, 31, 33, 49, 51, 52, 53, 55, 56, 57, 74, 77, 78, 84, 87, 97, 109, 111, 115, 134, 162 CFROM, 90, 112 Changeover, 2, 27, 28, 37, 106 Chirpcopy, 7, 14, 36, 99, 100 Clock, 4, 19, 38, 53, 54, 69, 70, 77, 83, 93, 135, 163, 167 CMSG, 75, 76, 78, 90, 91 Colors, 7, 13, 18, 29, 77, 93, 97, 115, 132, 133, 135, 144, 163 Connect, 2, 3, 4, 5, 6, 12, 13, 14, 18, 20, 22, 23, 25, 26, 27, 28, 29, 30, 34, 35, 38, 39, 41, 43, 44, 45, 46, 47, 48, 53, 54, 55, 56, 60, 62, 68, 69, 70, 72, 73, 76, 77, 79, 80, 81, 84, 89, 90, 102, 103, 104, 107, 112, 115, 117, 118, 119, 121, 123, 125, 128, 129, 130, 133, 136, 138 Connectee, 52, 138 CONOK, 76, 90 Contest, 4, 6, 13, 14, 19, 24, 29, 53, 54, 65, 77, 82, 83, 89, 138, 161, 166 Control-C, 50 Control-F, 120 Control-Q, 137 Control-S, 137 Control-Z, 3, 32 CONVERSE, 3, 9, 11, 30, 36, 58, 60, 70, 81, 104, 105, 106, 125, 135 CQ, 3, 6, 7, 9, 14, 15, 21, 23, 24, 25, 26, 28, 34, 35, 36, 38, 39, 41, 42, 44, 45, 78, 88, 89, 101, 103, 106, 107, 108, 109, 114, 115, 130, 132, 133, 135 CTEXT, 5, 7, 68, 69, 70, 75, 76, 78, 90, 114, 116, 125, 138 Customize, 17, 85, 90, 92, 93, 112, 128 DCD-Flag, 136 LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM, Page 170 DCDCONN, 104 Directories, 6, 77, 87, 103 DISCONNECTED, 10, 42, 45, 74, 80, 84, 103, 129, 136, 137 DSZ, 148, 158 DUPLEX, 11, 12 EAS, 118 Echo-As-Sent, 133 ELMER, 8, 9, 10, 12, 15, 25, 38, 112, 113, 114, 115, 116, 117, 122, 138, 139, 140, 142, 143, 144, 145, 146, 147, 163, 166 Expert, 10, 139, 140, 141, 142, 146, 163 FLOW, 20, 55, 57, 137, 156 FSK, 32 Greek, 10, 17, 93, 136 Header, 13, 22, 42, 46, 52, 68, 73, 84, 95, 105, 124, 129, 132, 133, 159, 160 Headers, 18, 20, 25, 42, 46, 73, 85, 102, 118, 152 Highlighted, 62, 63, 65, 147 Import-Convert, 5, 64, 65 Inwindow, 80, 94, 102, 144 IRQ, 92, 115, 116, 154, 158 KA-Node, 118, 119 KAM, 1, 9, 11, 18, 32, 36, 71, 72, 83, 87, 92, 93, 99, 100, 101, 103, 108, 110, 117, 118, 133, 135, 137, 138 KEYWORD, 113, 141, 142, 143, 145 KPC, 1, 9, 70, 132 LAMTOR, 8, 107 Link, 6, 12, 19, 22, 23, 25, 27, 32, 33, 34, 36, 37, 41, 43, 52, 59, 60, 61, 65, 77, 78, 80, 81, 82, 88, 99, 104, 105, 109, 111, 115, 120, 121, 122, 126, 127, 128, 129, 131, 135, 137, 162, 165 LOCAL-BBS, 52, 53, 71, 120 Log-to-disk, 77 Logs, 65, 135, 161 LogWindow, 94 Mail-Snatch, 6, 46, 85, 133 MBX, 8, 17, 60, 112, 114, 119, 130 MCON, 101, 138 Metabeacon, 8, 74, 75, 76, 105, 106, 138 MH, 3, 34, 77, 94, 125, 129, 132, 133, 138 MHWindow, 94 MON, 90, 156 MORSE, 7, 8, 11, 12, 15, 23, 24, 28, 31, 35, 99, 100, 107, 110, 111, 133 Multi-user, 46, 48, 102, 138 Multiconnect, 13, 36, 43, 70, 95, 96, 103, 104, 105, 132 LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM, Page 171 MYCALL, 107, 110, 111 NAVTEX, 7, 24, 99, 100, 138 NNNN, 109, 111 NODE, 6, 11, 14, 18, 43, 77, 80, 115 NTS, 48, 166 OUTwindow, 55, 94, 135, 144 Packet, 1, 2, 3, 7, 10, 11, 12, 13, 14, 20, 21, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 40, 41, 42, 43, 44, 45, 46, 52, 54, 55, 56, 60, 61, 62, 68, 70, 71, 72, 73, 74, 77, 78, 79, 80, 81, 83, 84, 85, 86, 87, 88, 89, 91, 92, 93, 95, 99, 101, 102, 105, 116, 117, 118, 123, 125, 126, 127, 128, 129, 130, 132, 133, 135, 136, 137, 138, 139, 162, 163, 166 PacketCluster, 2, 6, 15, 27, 30, 44, 87, 115, 117, 166 PacketClusterZap, 25 PCZ, 9, 10, 122, 127, 128, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159 QBM, 4, 6, 9, 58, 59, 87, 115, 124, 125, 128, 129 QBU, 4, 6, 9, 57, 58, 88, 115, 121, 128, 131, 138 QBU-RX, 6, 8, 58, 88, 114, 115, 121, 128 QBU-TX, 6, 9, 58, 88, 114, 115, 121, 128 QDB, 4, 9, 58, 59, 125, 128, 129 QJG, 9, 60, 130 QMH, 9, 13, 125, 126, 129, 132 QNO, 9, 58, 59, 81, 82, 124, 129, 130 QRA, 2, 4, 9, 14, 27, 30, 60, 129 QRM, 11, 35, 73, 78, 129 QRT, 7, 9, 23, 25, 73, 78, 90, 91, 112, 129, 130 QRU, 4, 9, 58, 60, 119, 129, 130 QRV, 7, 9, 58, 59, 90, 91, 123, 130 QRZ, 2, 3, 27, 30, 39, 75, 77 QSL, 9, 52, 58, 59, 61, 63, 73, 75, 77, 124, 130, 166 QSM, 4, 9, 22, 58, 59, 121, 129 QSO, 8, 9, 10, 12, 13, 21, 24, 26, 30, 33, 36, 45, 54, 57, 76, 78, 82, 83, 100, 102, 107, 109, 112, 113, 114, 122, 135, 139, 143, 145, 146, 147 QSP, 4, 6, 9, 25, 58, 59, 61, 77, 81, 114, 119, 123, 129, 130 QSY, 73, 78 QTA, 4, 9, 58, 60, 114, 121, 124, 130, 138 QTC, 6, 9, 13, 21, 22, 24, 25, 77, 79, 80, 81, 85, 115, 130 QTC-Snatch, 22, 23, 133 QYD, 9, 131 QYU, 9, 131 QZD, 4, 9, 58, 60, 61, 121, 127, 128, 131, 138 QZD-RX, 121, 127 QZD-TX, 121, 128 QZU, 4, 9, 58, 61, 121, 127, 128, 131, 138 QZU-RX, 121, 122, 127 QZU-TX, 121, 127 LAN-LINK.DOC (c) G3ZCZ 1988 - 1992 APPENDIX 11 LAN-LINK 2.00 REGISTRATION FORM, Page 172 ReMember, 3, 12, 41, 44, 82, 102, 105, 119, 150, 151 RTTY, 2, 5, 7, 15, 24, 30, 31, 32, 35, 71, 72, 99, 107, 109, 133, 138, 166 RXR, 71, 72 RY's, 27, 30, 138 SAREX, 5, 7, 14, 25, 71, 72, 73, 74, 75, 76, 77, 97, 115, 138 Scrollback, 2, 31, 138 ScrollBackWindow, 94 SELCAL, 6, 8, 14, 15, 24, 26, 27, 30, 36, 41, 43, 44, 45, 86, 87, 108, 109, 110, 114 Snatch, 6, 24, 25, 46, 47, 77, 79, 80, 81, 84, 115, 132 SOLO, 7, 25, 90, 91, 101, 102 StatusWindow, 94 Stream, 2, 27, 29, 75, 95, 96, 102, 103, 105, 115, 116, 117, 136 TheLink, 118 Time-of-day, 83 Time-out, 135 Timeout, 6, 89, 115, 117, 138 Traffic, 7, 20, 26, 60, 72, 73, 79, 85, 101, 102, 103, 136 Turing, 139 TXR, 71, 72 Type-ahead, 36 Unshift-on-space, 24 Upgrade, 20 Verbose, 85 XMITOK, 20, 100, 115, 117, 138 Zap, 2, 3, 4, 5, 7, 27, 30, 44, 46, 48, 51, 52, 53, 54, 71, 73, 74, 84, 85, 86, 97, 98, 99 ZapBBS, 24, 25, 84 Zapp, 41, 77 Zmodem, 9, 14, 60, 61, 121, 122, 127, 128, 131, 138, 148, 149, 150, 151, 152, 154, 156, 158, 159, 160 LAN-LINK.DOC (c) G3ZCZ 1988 - 1992